I can access the FRO in a C program via DoPCFloat(PC_COMM_SET_FRO,FRO); and change the feed rate override.

Is there a way to access the rapid override via C program in a similar way?

Andrew

Hi Andrew,

No that mechanism hasn't been added into KMotionCNC. If you really need this we can probably add that into the next Version.

Or your welcome to add it yourself :)

Regards

On 7/18/2016 8:29 PM, kn6za@... [DynoMotion] wrote:

I can access the FRO in a C program via DoPCFloat(PC_COMM_SET_FRO,FRO); and change the feed rate override.

Is there a way to access the rapid override via C program in a similar way?

Andrew

Thanks Tom,

I found the SetRapidFRO command, other than not changing the slider on GUI like the DoPCFloat, it does give me the ability to override the rapid rates on the machine.

I am not entirely sure what the difference between the DoPCFloat(PC_COMM_SET_FRO,FRO); and the SetRapidFRO besides not updating the slider in the GUI.

This is fine for me at this point, I can read an analog input from my rapid override knob and apply it to the machine so it works great.

PS, thanks for making these kflop/kanalog units available, it has completely updated my old machine! I am not a c programmer, but thanks to the various example programs and reading your answers to other folks questions I am up and running with a servo driven spindle no less!

Andrew

The difference between SetRapidFRO() and DoPCFloat() is that the first one is a direct function handled entirely in the kflop. The second one is actually exchanging data with the PC, telling it to perform the function rather than directly do it on the kflop. That's why it can update the slider, because it knows the intention of the command.

When you SetRapidFRO(), the PC doesn't necessarily know about it, so when you touch the rapid FRO slider on the PC, it is going to jump to whatever the slider says. If your kflop program is continuously updating the rapid FRO, from your analog control, then that should not be too noticeable except that the slider becomes ineffective. So it would be better to somehow inform the PC so it can keep the slider in sync. That would require a KMotionCNC change, as Tom mentioned.

Regards,

SJH

On Tue, Jul 19, 2016 at 8:40 PM, kn6za@... [DynoMotion] <DynoMotion@yahoogroups.com> wrote:

Thanks Tom,

I found the SetRapidFRO command, other than not changing the slider on GUI like the DoPCFloat, it does give me the ability to override the rapid rates on the machine.

I am not entirely sure what the difference between the DoPCFloat(PC_COMM_SET_FRO,FRO); and the SetRapidFRO besides not updating the slider in the GUI.

This is fine for me at this point, I can read an analog input from my rapid override knob and apply it to the machine so it works great.

PS, thanks for making these kflop/kanalog units available, it has completely updated my old machine! I am not a c programmer, but thanks to the various example programs and reading your answers to other folks questions I am up and running with a servo driven spindle no less!

Andrew

Thanks SJH,

That clarifies it greatly. Yes I did notice the slider became ineffective while the routine that read the analog channel and SetRapidFRO was running.

I will look into adding a DoPCFloat() for rapid rates.

It is nice having the rapid rate override on a knob now.

Andrew

Group: DynoMotion	Message: 13600	From: kn6za	Date: 7/18/2016
Subject: FRO, RRO?

Group: DynoMotion	Message: 13607	From: Tom Kerekes	Date: 7/19/2016
Subject: Re: FRO, RRO?

Group: DynoMotion	Message: 13614	From: kn6za	Date: 7/19/2016
Subject: Re: FRO, RRO?

Group: DynoMotion	Message: 13615	From: Hardy Family	Date: 7/19/2016
Subject: Re: FRO, RRO?

Group: DynoMotion	Message: 13616	From: kn6za	Date: 7/20/2016
Subject: Re: FRO, RRO?